-
Notifications
You must be signed in to change notification settings - Fork 8.2k
boards: posix: native_posix: enable can_loopback0 by default #50530
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
boards: posix: native_posix: enable can_loopback0 by default #50530
Conversation
henrikbrixandersen
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks. I left it as disabled since the loopback driver was not sufficient to run all the test suites back then. Should be fine now, though.
Ok, I see. Now we get several failing tests which were previously just not run. The counter sample should be excluded from the tests because it keeps running for ever and thus times out, but the ISO-TP failures may be actual issues with the loopback driver or ISO-TP itself. I'd suggest to exclude the native_posix board from the ISO-TP tests for now. |
cbab91a
fde03cd to
cbab91a
Compare
The .yaml file states that CAN is supported, but the basic sample application samples/drivers/can/counter cannot be compiled without additional configuration. The loopback driver does not require any additional steps like the linux SocketCAN driver, so it is safe to enable it by default and get rid of the many overlay files in the tests. ISO-TP tests and the counter sample are excluded via .yaml from twister tests because of timing issues. Signed-off-by: Martin Jäger <[email protected]>
cbab91a to
3a280ba
Compare
|
For some reason |
|
We really need to look into the ISO-TP protocol implementation post v3.2. The tests are failing on multiple boards. Either the implementation is flawed or the tests are. |
|
I have removed the "bug" label as I do not see this as a bug. We have filtering in place ( |
|
Hey, tagged for v3.3.0, feel free to update if you think this should be considered a bugfix. |
The .yaml file states that CAN is supported and
zephyr,canbusis chosen in the dts, but building the basic sample application samples/drivers/can/counter fails without additional configuration.The loopback driver does not require any additional steps like the linux SocketCAN driver, so it is safe to enable it by default and get rid of the many overlay files in the tests.